Managing data format of data received from devices in an internet of things network

ABSTRACT

The present disclosure relates to system(s) and method(s) for storing sensor data received from a device connected an Internet of Things (IoT) network. The system may store one or more record tables corresponding to one or more devices connected in an Internet of Things (IoT) network, in a database. Further, the system may receive a modification request from a device connected in the Internet of Things (IoT) network, wherein the modification request comprises a unique identification number corresponding to the device and a sensor configuration data. Further, the system may modify a table structure of a record table corresponding to the device to generate a modified table structure, based on the modification request. Further, the system may execute a programmed instruction stored in the memory to store the sensor data received from the device, in the record table, based on the modified table structure.

CROSS-REFERENCE TO RELATED APPLICATIONS AND PRIORITY

The present application claims priority from Indian Patent ApplicationNo. 201611019129 filed on 3 Jun. 2016, the entirety of which is herebyincorporated by reference.

TECHNICAL FIELD

The present disclosure in general relates to the field of Internet ofThings. More particularly, the present invention relates to managingdata captured from device in an Internet of Things (IoT) network.

BACKGROUND

Internet of Things (IoT) is nowadays used to fuse the physical anddigital worlds by bringing different concepts and technical componentstogether. Nowadays, IoT networks are used to create a seamless networkof billions of wireless identifiable objects that communicate with oneanother through wired or wireless communication means. The era of IoThas lead to the creation of a new ecosystem in which smart devices areenabled to adapt to their respective environments, self-configure,self-maintain and self-repair.

Modern IoT devices provide limited support for the integration ofthird-party peripherals. In order to solve this problem, plug-and-play(PnP) devices are now being developed which include hardware andsoftware components. PnP provides support for automatic integration ofthird-party peripherals. The PnP are constructed by stacking togethervarious hardware modules including power sources, processing units andsensors. The main processing unit automatically identifies all theattached modules and adjusts own operation accordingly. The completemodularity of the PnP devices allows users to choose the requiredfunctionality from different sensor modules.

With the introduction of PnP IoT devices existing IoT ecosystem needchanges to leverage the benefits of such devices. The current IoTecosystem is inefficient to leverage the benefits of PnP devices interms of platform communication and service offerings.

SUMMARY

This summary is provided to introduce aspects related to systems andmethods for storing sensor data received from a device connected anInternet of Things (IoT) network and the aspects are further describedbelow in the detailed description. This summary is not intended toidentify essential features of the claimed subject matter nor is itintended for use in determining or limiting the scope of the claimedsubject matter.

In one embodiment, a system for storing sensor data received from adevice connected an Internet of Things (IoT) network is illustrated. Thesystem comprises a processor coupled to a memory, wherein the processoris configured to execute programmed instructions stored in the memory.The processor may execute a programmed instruction stored in the memoryto store one or more record tables corresponding to one or more devicesconnected in an Internet of Things (IoT) network, in a database. In oneembodiment, each record table is assigned with a unique identificationnumber corresponding to a device of the one or more devices, wherein atable structure of the record table comprises one or more columnsconfigured to maintain sensor data received from one or more sensorsconnected to the device of the one or more device. Further, theprocessor may execute a programmed instruction stored in the memory toreceive a modification request from a device connected in the Internetof Things (IoT) network, wherein the modification request comprises aunique identification number corresponding to the device and a sensorconfiguration data corresponding to a sensor added to the device orremoved from the device. Further, the processor may execute a programmedinstruction stored in the memory to modify a table structure of a recordtable corresponding to the device to generate a modified tablestructure, based on the modification request. In one embodiment, themodified table structure of a record table is generated by adding newcolumn or deleting existing columns of the table structure, based on thesensor configuration data. Further, the processor may execute aprogrammed instruction stored in the memory to store the sensor datareceived from the device, in the record table, based on the modifiedtable structure.

In one embodiment, a method for storing sensor data received from adevice connected an Internet of Things (IoT) network is illustrated. Themethod may comprise storing one or more record tables corresponding toone or more devices connected in an Internet of Things (IoT) network, ina database. In one embodiment, each record table is assigned with aunique identification number corresponding to a device of the one ormore devices, wherein a table structure of the record table comprisesone or more columns configured to maintain sensor data received from oneor more sensors connected to the device of the one or more device. Themethod may further comprise receiving a modification request from adevice connected in the Internet of Things (IoT) network, wherein themodification request comprises a unique identification numbercorresponding to the device and a sensor configuration datacorresponding to a sensor added to the device or removed from thedevice. The method may further comprise modifying a table structure of arecord table corresponding to the device to generate a modified tablestructure, based on the modification request. In one embodiment, themodified table structure of a record table is generated by adding newcolumn or deleting existing columns of the table structure, based on thesensor configuration data. The method may further comprise storing thesensor data received from the device, in the record table, based on themodified table structure.

In one embodiment, a non-transitory computer readable medium embodying aprogram executable in a computing device for storing sensor datareceived from a device connected an Internet of Things (IoT) network isillustrated. The program comprises a program code for storing one ormore record tables corresponding to one or more devices connected in anInternet of Things (IoT) network, in a database. In one embodiment, eachrecord table is assigned with a unique identification numbercorresponding to a device of the one or more devices, wherein a tablestructure of the record table comprises one or more columns configuredto maintain sensor data received from one or more sensors connected tothe device of the one or more device. The program comprises a programcode for receiving a modification request from a device connected in theInternet of Things (IoT) network, wherein the modification requestcomprises a unique identification number corresponding to the device anda sensor configuration data corresponding to a sensor added to thedevice or removed from the device. The program comprises a program codefor modifying a table structure of a record table corresponding to thedevice to generate a modified table structure, based on the modificationrequest. In one embodiment, the modified table structure of a recordtable is generated by adding new column or deleting existing columns ofthe table structure, based on the sensor configuration data. The programcomprises a program code for storing the sensor data received from thedevice, in the record table, based on the modified table structure.

BRIEF DESCRIPTION OF DRAWINGS

The detailed description is described with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Thesame numbers are used throughout the drawings to refer like features andcomponents.

FIG. 1 illustrates a network implementation of a system for storingsensor data received from a device connected an Internet of Things (IoT)network, in accordance with an embodiment of the present subject matter.

FIG. 2 illustrates the system for storing sensor data received from adevice connected an Internet of Things (IoT) network, in accordance withan embodiment of the present subject matter.

FIG. 3 illustrates a flow diagram for storing sensor data received froma device connected an Internet of Things (IoT) network, in accordancewith an embodiment of the present subject matter.

FIG. 4 illustrates format of a modification request for modifying tablestructure of a record table, in accordance with an embodiment of thepresent subject matter.

FIG. 5 illustrates a sequence diagram detailing the steps forprovisioning a device in the IoT network and modifying the structure ofthe record table, in accordance with an embodiment of the presentsubject matter.

DETAILED DESCRIPTION

The present subject matter relates to a system for storing sensor datareceived from a device connected an Internet of Things (IoT) network.The system is configured to store one or more record tablescorresponding to one or more devices connected in an Internet of Things(IoT) network, in a database. In one embodiment, each record table isassigned with a unique identification number corresponding to a deviceof the one or more devices, wherein a table structure of the recordtable comprises one or more columns configured to store sensor datareceived from one or more sensors connected to the device of the one ormore device.

In one embodiment, the record table may be generated after receiving aconnection request and the table structure from the device, wherein eachcolumn in the table structure is assigned with a data type and a dataattribute corresponding to a sensor of the one or more sensors. The datatype comprises an integer, a float, a text, and a double, and whereinthe data attributes comprise temperature, humidity, speed, acceleration,direction, and proximity. Once the request is received, in the nextstep, a record table is generated based on the connection request andthe table structure. Further, the system is configured to assigning theunique identification number to the record table. Once the uniqueidentification number is assigned, in the next step, the uniqueidentification number is transmitted to the device for futurecommunication.

The system is further configured for receiving a modification requestfrom a device connected in the Internet of Things (IoT) network, whereinthe modification request comprises a unique identification numbercorresponding to the device and a sensor configuration datacorresponding to a sensor added to the device or removed from thedevice. The method may further comprise modifying a table structure of arecord table corresponding to the device to generate a modified tablestructure, based on the modification request. In one embodiment, themodified table structure of a record table is generated by adding newcolumn or deleting existing columns of the table structure, based on thesensor configuration data. The method may further comprise storing thesensor data received from the device, in the record table, based on themodified table structure.

In the existing art, IoT based PnP systems are not equipped to supportPnP devices where data format is not constant and can't be defined atthe time of provisioning itself. In the PnP systems as a new sensormodule is added to main controller, device format is updated. If we tryto Provision PnP devices with existing system, we need to re-registerevery time there is change in data format. Due to this different deviceIDs are generated for same device and as a result historical data forthe device is lost. As IoT is all about data and data processing, losingdata due to change in device ID may lead to huge amount of losses.

To address this problem, the system is configured to assign uniqueidentification number and a table structure duringprovisioning/registration of each device with the system. The tablestructure of the record table corresponding to the device may be changedbased on the change in the sensors attached to the device, withoutre-registration to prevent any data losses. The present system allowsflexibility to change device data format dynamically even after theprovisioning process is completed. Further, the system is configured tomodify storage as per change in device data format at run-time.

While aspects of described system and method for storing sensor datareceived from a device connected an Internet of Things (IoT) network maybe implemented in any number of different computing systems,environments, and/or configurations, the embodiments are described inthe context of the following exemplary system.

Referring now to FIG. 1, a network implementation 100 of a system 102for storing sensor data received from a device connected an Internet ofThings (IoT) network is disclosed. Although the present subject matteris explained considering that the system 102 is implemented on a server,it may be understood that the system 102 may also be implemented in avariety of computing systems, such as a laptop computer, a desktopcomputer, a notebook, a workstation, a mainframe computer, a server, anetwork server, and the like. In one implementation, the system 102 maybe implemented in a cloud-based environment. It will be understood thatthe system 102 may be accessed by a primary user through one or moreuser devices 104-1, 104-2 . . . 104-N, collectively referred to as userdevices 104 hereinafter, or applications residing on the user devices104. Examples of the user devices 104 may include, but are not limitedto, a portable computer, a personal digital assistant, a handhelddevice, and a workstation, file server, version control servers, bugstracking servers. The user devices 104 are communicatively coupled tothe system 102 through a network 106.

In one implementation, the network 106 may be a wireless network, awired network or a combination thereof. The network 106 can beimplemented as one of the different types of networks, such as intranet,local area network (LAN), wide area network (WAN), the internet, and thelike. The network 106 may either be a dedicated network or a sharednetwork. The shared network represents an association of the differenttypes of networks that use a variety of protocols, for example,Hypertext Transfer Protocol (HTTP), Transmission ControlProtocol/Internet Protocol (TCP/IP), Wireless Application Protocol(WAP), and the like, to communicate with one another. Further thenetwork 106 may include a variety of network devices, including routers,bridges, servers, computing devices, storage devices, and the like.

Further, the system 102 is connected to one or more devices hereafterreferred to as a set of devices 110. In one embodiment, the set ofdevices 110 are connected to the system 102 through an internet ofthings network. In one embodiment, the set of devices 110 are configuredto transmit sensor data captured from one or more sensors attached tothe set of devices 110. Further, the system is configured maintain thesensor data captured from each device of the set of devices in a recordtable. Furthermore, the system is configured to modify the tablestructure of the record table based on modification brought to thesensors attached to the device of the set of devices 110. The process ofstoring sensor data received from a device connected an Internet ofThings (IoT) network is further elaborated with respect to FIG. 2.

Referring now to FIG. 2, the system 102 is illustrated in accordancewith an embodiment of the present subject matter. In one embodiment, thesystem 102 may include at least one processor 202, an input/output (I/O)interface 204, and a memory 206. The at least one processor 202 may beimplemented as one or more microprocessors, microcomputers,microcontrollers, digital signal processors, central processing units,state machines, logic circuitries, and/or any devices that manipulatesignals based on operational instructions. Among other capabilities, theat least one processor 202 is configured to fetch and executecomputer-readable instructions stored in the memory 206.

The I/O interface 204 may include a variety of software and hardwareinterfaces, for example, a web interface, a graphical user interface,and the like. The I/O interface 204 may allow the system 102 to interactwith a user directly or through the user devices 104. Further, the I/Ointerface 204 may enable the system 102 to communicate with othercomputing devices, such as web servers and external data servers (notshown). The I/O interface 204 can facilitate multiple communicationswithin a wide variety of networks and protocol types, including wirednetworks, for example, LAN, cable, etc., and wireless networks, such asWLAN, cellular, or satellite. The I/O interface 204 may include one ormore ports for connecting a number of devices to one another or toanother server.

The memory 206 may include any computer-readable medium known in the artincluding, for example, volatile memory, such as static random accessmemory (SRAM) and dynamic random access memory (DRAM), and/ornon-volatile memory, such as read only memory (ROM), erasableprogrammable ROM, flash memories, hard disks, optical disks, andmagnetic tapes. The memory 206 may include modules 208 and data 210.

The modules 208 include routines, programs, objects, components, datastructures, etc., which perform particular tasks, functions or implementparticular abstract data types. In one implementation, the modules 208may include a provisioning module 212, a request capturing module 214, amodification module 216, a data maintenance module 218, and othermodules 220. The other modules 220 may include programs or codedinstructions that supplement applications and functions of the system102. The data 210, amongst other things, serves as a repository forstoring data processed, received, and generated by one or more of themodules 208. The data 210 may also include a local repository 226, andother data 228. The local repository 226 is configured to store therecord table corresponding to each device from the set of devices 110that are generated by the provisioning module 212.

In one implementation, the provisioning module 212 is configured tostore one or more record tables corresponding to the set of device 110in an Internet of Things (IoT) network, in the local repository 226. Inone embodiment, the provisioning module 212 is configured to assign eachrecord table with a unique identification number corresponding to adevice of the one or more devices. In one embodiment, a table structureof the record table comprises one or more columns configured to maintainsensor data received from one or more sensors connected to the device ofthe set of device 110.

In one embodiment, the record table for a device may be generated by theprovisioning module 212 after receiving a connection request and thetable structure from the device of the set of device 110. In oneembodiment, the provisioning module 212 may assign each column in thetable structure with a data type and a data attribute corresponding to asensor of the one or more sensors attached to the device. The data typecomprises an integer, a float, a text, and a double. The selection ofthe data type corresponding to the column is based on the type and sizeof data received from the sensor corresponding to the column. Forexample, if a speedometer sensor is connected to the device, then thedata type selected for the column corresponding to the sensor may beinteger. However, in case of a temperature sensor, the data type may befloat.

Further, the data attributes comprise temperature, humidity, speed,acceleration, direction, and proximity. The data attribute defines thetype of information collected from the sensor. Once the request isreceived, in the next step, a record table is generated by theprovisioning module 212, based on the connection request and the tablestructure. Further, the provisioning module 212 is configured toassigning the unique identification number to the record table. Once theunique identification number is assigned, in the next step, the uniqueidentification number is transmitted to the device for futurecommunication.

Further, the request capturing module 214 is configured to receive amodification request from a device connected in the Internet of Things(IoT) network. The modification request may comprise a uniqueidentification number corresponding to the device and a sensorconfiguration data corresponding to a sensor added to the device orremoved from the device. The request capturing module 214 is configuredto analyse the request and fetch information corresponding to the recordtable associated with the unique identification number in the request.

Further, the modification module 216 is configured to modify the tablestructure of the record table corresponding to the device to generate amodified table structure, based on the modification request. In oneembodiment, the modified table structure of a record table is generatedby adding new column or deleting existing columns of the tablestructure, based on the sensor configuration data in the modificationrequest. For example, if a new temperature sensor is added to thedevice, then the information associated with the new temperature sensorin the form of sensor configuration data is transmitted to themodification module 216. The modification module 218 in response adds acolumn to the record table for storing data captured from the newtemperature sensor.

In one embodiment, once the table structure is updated to generatemodified table structure, in the next step the data maintenance module218 is configured to store the sensor data received from the device, inthe record table, based on the modified table structure. The method forstoring sensor data received from a device connected an Internet ofThings (IoT) network is further illustrated with respect to the blockdiagram of FIG. 3.

Referring now to FIG. 3, a method 300 for storing sensor data receivedfrom a device connected an Internet of Things (IoT) network isdisclosed, in accordance with an embodiment of the present subjectmatter. The method 300 may be described in the general context ofcomputer executable instructions. Generally, computer executableinstructions can include routines, programs, objects, components, datastructures, procedures, modules, functions, and the like, that performparticular functions or implement particular abstract data types. Themethod 300 may also be practiced in a distributed computing environmentwhere functions are performed by remote processing devices that arelinked through a communications network. In a distributed computingenvironment, computer executable instructions may be located in bothlocal and remote computer storage media, including memory storagedevices.

The order in which the method 300 is described is not intended to beconstrued as a limitation, and any number of the described method blockscan be combined in any order to implement the method 300 or alternatemethods. Additionally, individual blocks may be deleted from the method300 without departing from the spirit and scope of the subject matterdescribed herein. Furthermore, the method 300 can be implemented in anysuitable hardware, software, firmware, or combination thereof. However,for ease of explanation, in the embodiments described below, the method300 may be considered to be implemented in the above described system102.

At block 302, the provisioning module 212 is configured to store one ormore record tables corresponding to the set of device 110 in an Internetof Things (IoT) network, in the local repository 226. Further, theprovisioning module 212 is configured to assign each record table with aunique identification number corresponding to a device of the one ormore devices. In one embodiment, a table structure of the record tablecomprises one or more columns configured to maintain sensor datareceived from one or more sensors connected to the device of the set ofdevice 110.

In one embodiment, the record table for a device may be generated by theprovisioning module 212 after receiving a connection request and thetable structure from the device of the set of device 110. In oneembodiment, the provisioning module 212 may assign each column in thetable structure with a data type and a data attribute corresponding to asensor of the one or more sensors attached to the device. The data typecomprises an integer, a float, a text, and a double. The selection ofthe data type corresponding to the column is based on the type and sizeof data received from the sensor corresponding to the column. Forexample, if a speedometer sensor is connected to the device, then thedata type selected for the column corresponding to the sensor may beinteger. However, in case of a temperature sensor, the data type may befloat.

Further, the data attributes comprise temperature, humidity, speed,acceleration, direction, and proximity. The data attribute defines thetype of information collected from the sensor. Once the request isreceived, in the next step, a record table is generated by theprovisioning module 212, based on the connection request and the tablestructure. Further, the provisioning module 212 is configured toassigning the unique identification number to the record table. Once theunique identification number is assigned, in the next step, the uniqueidentification number is transmitted to the device for futurecommunication.

At block 304, the request capturing module 214 is configured to receivea modification request from a device connected in the Internet of Things(IoT) network. The modification request may comprise a uniqueidentification number corresponding to the device and a sensorconfiguration data corresponding to a sensor added to the device orremoved from the device. The request capturing module 214 is configuredto analyse the request and fetch information corresponding to the recordtable associated with the unique identification number in the request.

At block 306, the modification module 216 is configured to modify thetable structure of the record table corresponding to the device togenerate a modified table structure, based on the modification request.In one embodiment, the modified table structure of a record table isgenerated by adding new column or deleting existing columns of the tablestructure, based on the sensor configuration data in the modificationrequest. For example, if a new temperature sensor is added to thedevice, then the information associated with the new temperature sensorin the form of sensor configuration data is transmitted to themodification module 216. The modification module 218 in response adds acolumn to the record table for storing data captured from the newtemperature sensor.

At block 308, once the table structure is updated to generate modifiedtable structure, in the next step the data maintenance module 218 isconfigured to store the sensor data received from the device, in therecord table, based on the modified table structure. The format of themodification request is further explained with respect to FIG. 4.

FIG. 4 represents format of the modification request for modifying thetable structure of the record table. The request comprises a uniqueidentification number also referred to as Device GUID. The Device GUIDuniquely identifies device and is shared during enrolment process.Further, the modification request comprises action parameter comprisingsensor add, sensor delete, and sensor data. Based on the actionparameter the modification module 216 identifies whether themodification request is for adding new sensor data format, or existingsensor removed or aggregated sensor value and takes action based on thesame.

Further, the third parameter contains information corresponding to theaction parameter. If the action parameter is for adding new sensor, thethird parameter contains data format and data size corresponding to thenew sensor. If the action parameter is for removing existing sensor, thethird parameter contains sensor name to be removed from the recordtable. If the action parameter is for adding data to the record table,the third parameter contains aggregated sensor values separated by commato be added to the record table.

Referring now to FIG. 5, a sequence diagram detailing the differentsteps involved in provisioning a device in the IoT network and modifyingthe structure of the record table corresponding to the record tablebased on adding or deleting sensors is disclosed.

Although implementations for methods and systems for storing sensor datareceived from a device connected an Internet of Things (IoT) network hasbeen described, it is to be understood that the appended claims are notnecessarily limited to the specific features or methods described.Rather, the specific features and methods are disclosed as examples ofimplementations for storing sensor data received from a device connectedan Internet of Things (IoT) network.

We claim:
 1. A method for storing sensor data received from a deviceconnected to an Internet of Things (IoT) network, the method comprising:storing, by a processor, one or more record tables corresponding to oneor more devices connected in an Internet of Things (IoT) network,wherein each record table is assigned with a unique identificationnumber corresponding to the device of the one or more devices, andwherein a table structure of the record table comprises one or morecolumns configured to maintain sensor data received from one or moresensors connected to the device of the one or more devices; receiving,by the processor, a modification request from the device connected inthe Internet of Things (IoT) network, wherein the modification requestcomprises the unique identification number corresponding to the deviceand a sensor configuration data corresponding to a sensor added to thedevice or removed from the device; modifying, by the processor, thetable structure of the record table corresponding to the device togenerate a modified table structure, based on the modification request,wherein the modified table structure of the record table is generated byadding new column or deleting existing columns of the table structure,based on the sensor configuration data, to provide a Plug and Play (PnP)environment; and storing, by the processor, the sensor data receivedfrom the device, in the record table, based on the modified tablestructure.
 2. The method of claim 1, wherein the one or more recordtables are maintained in a database.
 3. The method of claim 1, whereinthe method further comprising receiving, by a processor, a connectionrequest and the table structure from the device; generating, by theprocessor, a record table based on the connection request and the tablestructure; assigning, by the processor, the unique identification numberto the record table; and transmitting, by the processor, the uniqueidentification number to the device.
 4. The method of claim 1, whereineach column in the table structure is assigned with a data type and adata attribute corresponding to a sensor of the one or more sensors,wherein the data type comprises an integer, a float, a text, and adouble, and wherein the data attributes comprise temperature, humidity,speed, acceleration, direction, and proximity.
 5. A system for storingsensor data received from a device connected to an Internet of Things(IoT) network, the system comprising: a memory; and a processorconnected to the memory, wherein the processor is configured to executeprogrammed instructions stored in the memory to: store one or morerecord tables corresponding to one or more devices connected in anInternet of Things (IoT) network, wherein each record table is assignedwith a unique identification number corresponding to the device of theone or more devices, and wherein a table structure of the record tablecomprises one or more columns configured to maintain sensor datareceived from one or more sensors connected to the device of the one ormore devices; receive a modification request from the device connectedin the Internet of Things (IoT) network, wherein the modificationrequest comprises the unique identification number corresponding to thedevice and a sensor configuration data corresponding to a sensor addedto the device or removed from the device; modify the table structure ofthe record table corresponding to the device to generate a modifiedtable structure, based on the modification request, wherein the modifiedtable structure of the record table is generated by adding new column ordeleting existing columns of the table structure, based on the sensorconfiguration data, to provide a Plug and Play (PnP) environment; andstore the sensor data received from the device, in the record table,based on the modified table structure.
 6. The system of claim 5, whereinthe one or more record tables are maintained in a database.
 7. Thesystem of claim 5, further configured to: receive a connection requestand the table structure from the device; generate a record table basedon the connection request and the table structure; assign the uniqueidentification number to the record table; and transmit the uniqueidentification number to the device.
 8. The system of claim 5, whereineach column in the table structure is assigned with a data type and adata attribute corresponding to a sensor of the one or more sensors,wherein the data type comprises an integer, a float, a text, and adouble, and wherein the data attributes comprise temperature, humidity,speed, acceleration, direction, and proximity.
 9. A non-transitorycomputer readable medium embodying a program executable in a computingdevice for storing sensor data received from a device connected to anInternet of Things (IoT) network, the computer program productcomprising: a program code for storing one or more record tablescorresponding to one or more devices connected in an Internet of Things(IoT) network, wherein each record table is assigned with a uniqueidentification number corresponding to the device of the one or moredevices, and wherein a table structure of the record table comprises oneor more columns configured to maintain sensor data received from one ormore sensors connected to the device of the one or more devices; aprogram code for receiving a modification request from the deviceconnected in the Internet of Things (IoT) network, wherein themodification request comprises the unique identification numbercorresponding to the device and a sensor configuration datacorresponding to a sensor added to the device or removed from thedevice; a program code for modifying the table structure of the recordtable corresponding to the device to generate a modified tablestructure, based on the modification request, wherein the modified tablestructure of the record table is generated by adding new column ordeleting existing columns of the table structure, based on the sensorconfiguration data, to provide a Plug and Play (PnP) environment; and aprogram code for storing the sensor data received from the device, inthe record table, based on the modified table structure.